Greptile Summary

This PR fixes a regression from #9779 where mise upgrade's final summary could be erased by the progress UI on process shutdown. The root cause was that fresh progress jobs created during old-version uninstall cleanup were still registered with clx when print_summary ran, so stop_clear() at shutdown could wipe the detail lines.

• finish_progress() is extracted as a public method on MultiProgressReport, calling progress::stop() then reset_jobs() to render the last state and deregister all jobs from clx.
• Two finish_progress() calls are added in upgrade.rs: one after the uninstall loop and a defensive second one immediately before print_summary(), covering any new jobs created by rebuild_shims_and_runtime_symlinks or PIPXBackend::reinstall_all.
• A new e2e regression test sets MISE_FORCE_PROGRESS=1, runs mise up dummy, and verifies that no ANSI erase-in-display sequence (ESC[…J) appears in the output after the summary line.

Confidence Score: 5/5

Safe to merge — the change is narrowly scoped to progress job lifecycle management and is protected by a targeted regression test.

The fix correctly stops and deregisters progress jobs before printing the upgrade summary, and the double finish_progress() calls are harmless because reset_jobs() leaves clx's job list empty for the second call. The e2e test exercises the exact failure mode described in the root-cause analysis.

No files require special attention.

Important Files Changed

_{Reviews (2): Last reviewed commit: "test(upgrade): clarify progress summary ..." | Re-trigger Greptile}